Preserve query as Parquet file-level metadata - #2228
Merged
Conversation
Since the Parquet file format supports file-level metadata, when saving a Parquet with .>, we can preserve the originating query in the file. The .> operator and target filename are preserved in the query, which might be debatable. The Polars documentation also warns that the metadata interface is experimental, but our tests should catch any issues on a dependency upgrade.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Since the Parquet file format supports file-level metadata, when saving a Parquet with
.>, we can preserve the originating query in the file.The
.>operator and target filename are preserved in the query, which might be debatable.The Polars documentation also warns that the metadata interface is experimental, but our tests should catch any issues on a dependency upgrade.
Example of viewing the file-level metadata in the produced Parquet using the tool parqeye:
Checklist
changelog.mdfile.AUTHORSfile (or it's already there).